Update CreatePipelineConfigurationParameters model #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
regenerate after fix for byte array data
bump version to 0.1.7
fix git get_commit_diffs query parameters
regen 4.1 apis after fix to include 'action' in route dictionary.
regen 4.0 apis after fix to include 'action' in route dictionary.
bump version number to 0.1.8
…point,Symbol, Wiki, WIT Process, WIT Process Def, WIT Process Template
Add new 4.0 and 4.1 REST areas: CLT, Graph, MEM, Profile, Service Endpoint, Symbol, Wiki, WIT Process, WIT Process Def, WIT Process Template
bump version to 0.1.9
bump version to 0.1.10
add User area for 4.1 api
change release_trigger_base into a property bag.
bump version to 0.1.11
… which is intended to only be used to make s2s calls.
add Members Entitlement Management to manage users. remove user area,…
Bump version to 0.1.12
bump VERSION = "5.1.0b5"
…rsal becomes upack_api
fix issue microsoft#280, fix naming of upack_api_client folder: universal becomes upack_api
…if it does not exist at the organization level.
…would have happened if we were already using a deployment url.
Fix for issue microsoft#289 - check for location at deployment level if it does not exist at the organization level.
bump VERSION = "5.1.0b6"
* Create pythonpackage.yml
* add python v3.8
* 6.0 API
Regenerate after fixing float type handling in generator
update apis to match 6.0 RTW
* fix for issue microsoft#354 * catch OSError instead of FileExistsError, since FileExistsError is not available in python 2.7
* fix for issue microsoft#354 * catch OSError instead of FileExistsError, since FileExistsError is not available in python 2.7 * Revert "update apis to match 6.0 RTW" This reverts commit 5428142. * regen 6.0 as preview * bump version
In the current state, I'm receiving below error when using the create_pipeline since the serialized payload is not correct. "This API does not support creating pipelines of configuration type Yaml." Update the model required to create new pipeline.
|
This field might be case sensitive, did you try lower case Also Was it on-prem or Azure DevOps, and which version? |
|
Even Azure's own documentation is wildly out of date here. The current HTTP body schema I've found for "name": "pipeline-name",
"configuration": {
"type": "yaml",
"path": "pipline.yaml",
"repository": {
"id": "my-repo-guid",
"type": "azureReposGit",
"name": "repo-name"
}
},
"folder": "path/to/my/pipeline", |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current state, I'm receiving below error when using the create_pipeline since the serialized payload is not correct.
"This API does not support creating pipelines of configuration type Yaml."
Update the model required to create new pipeline.